vk: Handle VK_ERROR_FRAGMENTATION when allocating descriptor pools #14012
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The intel driver only support 1 million descriptor objects (we use update-after-bind everywhere) which sounds like a lot until you consider that we consume something like 50 of them every draw call. The moment a complex scene appears the driver implodes.
This fix adds a fallback in the form of a full stall to reset the queues. The downside to this is that intel GPUs will never be able to render high-draw-call-count titles at any reasonable framerates. Anything with over 10k draws will just crater.
Fixes #13997